…ed to Box.

Precursor for landing overloaded-`box`, since that will decouple the
`box` syntax from the exchange heap (and in fact will eliminate the
use of the two aforementioned lang items).

Instead, the new demonstration program shows a definition of the
`panic_bounds_check` lang item. (We do not have that many procedural
lang-items to choose from, which is a good sign for our efforts to
decouple the compiler from the runtime!)

Only one case is used in the text.  All of them are pretty straightforward, so
I don't think the code needs an explicit link to the README.

Update from straight line to reference-style link.

The Rust Reference should include the tuple indexing (using a number
as a field) notation; currently it is only available on
http://doc.rust-lang.org/std/primitive.tuple.html and not easily
searchable.

- Various grammatical changes.
- Use triple-backtick syntax and sh highlighting for code blocks.
- Fix indentation of code block in step 2 of "Building on Windows".
- Use title case for "Getting Help" subheading.

Fixes rust-lang#22152

Fixed example threaded code in intro doc never printing results. Threads were created with Thread::spawn instead of Thread::scoped.

Fixes rust-lang#22152

…ture, r=Manishearth

This is a patch for rust-lang#17829.

In `compiletest` there are multiple layers which capture the output. The first layer is  `run_tests_console` which is used to execute all tests.

Then there are some tests that contain unit tests, which by default also captures output. Therefore `compiletest` adds `RUST_TEST_NOCAPTURE` (and `RUST_TEST_TASKS` for completeness) to the run environment of the task.

Finally, the task used to execute a test redirects stdout and stdin. At the moment, the `VERBOSE=1` prints all captured output of the task (but has to print stdout and stderr separately). So at the moment using `RUST_TEST_NOCAPTURE=1` only makes sense when also using `VERBOSE=1` which seems a little bit cumbersome.

Should I update the patch to only print the output of the tasks that actually execute the test (`VERBOSE=1` includes other stuff, like the output of the task used to compile the test)? This will probably involve adding an extra flag to some functions in `src/compiletest/runtest.rs` to distinguish compilation runs from runs that execute the actual tests.

…teveklabnik

Fixed example threaded code in intro doc never printing results. Threads were created with Thread::spawn instead of Thread::scoped. Also added correct thread handling like in the first example of the document.

Clarify that `to_string` is how you make `String`. Use a coercion in an example.

r? @steveklabnik

…matsakis

And minor fixes to other docs.

r? @nikomatsakis

r? @steveklabnik

r? @steveklabnik

r? @steveklabnik 

I've updated the iterators chapter to reflect the fact that you can now iterate over `for` loops without calling `.iter()`.

r? @huonw

…hton

It looks like a few spots in the documentation were missed when renaming `Bitv` and `BitvSet`. This fixes the docs to use their current names.

Update from straight line to reference-style link.

fix issue rust-lang#22535

…chton

The Rust Reference should include the tuple indexing (using a number
as a field) notation; currently it is only available on
http://doc.rust-lang.org/std/primitive.tuple.html and not easily
searchable.

- Various grammatical changes.
- Use triple-backtick syntax and `sh` highlighting for code blocks.
- Fix indentation of code block in step 2 of "Building on Windows".
- Use title case for "Getting Help" subheading.

None

r? @huonw